R06. Warning and handling when loading files

The following warning message may occur when using profile division/model file division of the team collaboration function. If a warning message is displayed when loading the project file and model file, take the actions described below.

Warning message list

No. Title/Category Warning Message
1 Reference not found Model: No reference found from Model1 (model for Field1 field).
2 Models with duplicate internal IDs cannot be loaded Models: Model1 (File1) and models with duplicate internal IDs: Model2 (File2) cannot be loaded.
3 Warning when loading file Warning: The model: Model1 (File1) cannot be loaded because the metamodel is not found in the profile.
4 WARNINGS WHEN LOADING FILE WARNING: Unable to load association for model: Model1 and model: Model2 because the metamodel is not found in profile.
5 Warning when reading the file Warning: The field of model: Model1 cannot be read because the field definition of class: Class1 cannot be found in the profile.
6 Warning when loading file WARNING: The Field1 of model: Model1 and the related field of Field2 of model: Model2 cannot be read because the field definition for the related class: Class1 cannot be found in the profile.
7 Warning when loading file WARNING: View of Model1 cannot be displayed because the view definition cannot be found.
8 File Loading Warning WARNING: Cannot view the associated view for Field1 in Model: Model1 and Field2 in Model: Model2 because the view definition is missing.

Workaround

1. Model: The reference destination (Model of Field1 field) from Model1 cannot be found.

Cause

  • Referenced model does not exist

Occurrence conditions

  • When the model that was referenced between the divided model files is deleted and only the referenced model file is restored to the revision before the model was deleted.

  • Same for reference between project file and model file

Workaround

  • Restore the referenced model file or project file to the revision before deleting the model, and then reopen the project.

  • If the referenced model is not required, jump to the relevant part from the warning message, or display the relevant model and delete the element displayed as "(Could not be loaded)".

2. Model: Model1 (File1) and internal ID duplicate: Model: Model2 (File2) cannot be read.

Cause

  • There are multiple models with the same internal ID

Occurrence conditions

  • After moving a model between split model files or between a project file and a model file, only the source file is reverted to the revision before the model was moved.

  • When the model file or project file containing the parent model is restored to the revision before the split after splitting the child model from the parent-child relationship model into another model file

Workaround

  • Update the File1 and File2 model files that contain duplicate models to the latest revision, then reopen the project.

  • If the latest revision is not available, use one of the following methods to delete one model, save the file, then reopen the project.

    • If you want to delete Model1 and leave Model2, jump to the relevant part from the warning message and delete Model1.

    • If you want to delete Model2 and leave Model1, delete it as follows.

      (1) If File1 is a project file, Model1 is divided into model files. (2) Integrate the model file of File2 into the project file, and then reopen the project. (3) Although a warning message is displayed, Model2 is loaded and Model1 is not loaded. (4) Jump to the relevant part from the warning message and delete Model2. (5) If you save the file and then reopen the project, Model1 is read and displayed, and the warning message does not appear. (6) If there are duplicate internal IDs in more than two models, repeat the above steps.

3. Warning: The model: Model1 (File1) cannot be loaded because the metamodel is not found in the profile.

Cause

  • The underlying model entity is not defined in the metamodel

Occurrence conditions

  • If the file containing the profile (project file or profile file) has not been updated to the latest revision

  • When the profile and the model are divided into files, a new entity is defined in the metamodel, a model based on the entity is added, and then only the file containing the profile is returned to the revision before the entity definition.

Workaround

  • Update the file containing the profile to the latest revision, then reopen the project.

  • If you do not need the corresponding model, please do the "File Cleanup" below.

4. WARNING: Model: Model1 and Model: Model2 association cannot be loaded because the metamodel is not found in the profile.

Cause

  • Relationship between models is not defined in metamodel

Occurrence conditions

  • If the file containing the profile (project file or profile file) has not been updated to the latest revision

  • With the profile and model split into files, after defining a new reference relation or derived relation in the metamodel and adding a relation based on it, only the file containing the profile is set to the revision before the relation definition. When returning

Workaround

  • Update the file containing the profile to the latest revision, then reopen the project.

  • If you do not need the relevant association, please do the "File Cleanup" below.

5. Warning: The field of model: Model1 cannot be read because the field definition of class: Class1 cannot be found in the profile.

Cause

  • Model field not defined in metamodel

Occurrence conditions

  • If the file containing the profile (project file or profile file) has not been updated to the latest revision

  • When the profile and the model are divided into files, and after defining a new field in the entity of the metamodel, only the file containing the profile is reverted to the revision before the field definition.

Workaround

  • Update the file containing the profile to the latest revision, then reopen the project.

  • If you do not need the corresponding fields, please do the "File Cleanup" below.

6. WARNING: The field definition for model: Model1 and field2 for model: Model2 cannot be read because the field definition for the related class: Class1 cannot be found in the profile. Hmm.

Cause

  • Related field not defined in metamodel

Occurrence conditions

  • If the file containing the profile (project file or profile file) has not been updated to the latest revision

  • When the profile and model are split into files, and after defining a new field in the metamodel association, only the file containing the profile is restored to the revision before the field definition.

Workaround

  • Update the file containing the profile to the latest revision, then reopen the project.

  • If you do not need the relevant fields, please do the "File Cleanup" below.

7. Warning: The view for Model1 cannot be displayed because the view definition cannot be found.

Cause

  • Entity view definition is not defined in profile

Occurrence conditions

  • If the file containing the profile (project file or profile file) has not been updated to the latest revision

  • When profile and model are divided into files, and after defining a new view, only the file containing the profile is reverted to the revision before the view definition.

Workaround

  • Update the file containing the profile to the latest revision, then reopen the project.

  • If you do not need the corresponding view, please do the "File Cleanup" below.

8. Warning: Unable to display the associated views for Field1 of Model: Model1 and Field2 of Model: Model2 because the view definition cannot be found.

Cause

  • No related view definition defined in profile

Occurrence conditions

  • If the file containing the profile (project file or profile file) has not been updated to the latest revision

  • When the profile and model are split into files, and after defining a new related view, only the file containing the profile is reverted to the revision before the view definition.

Workaround

  • Update the file containing the profile to the latest revision, then reopen the project.

  • If you do not need the relevant view, please do the "File Cleanup" below.

File cleanup

Use the following procedure to delete unnecessary data from the project file and model file.

File cleanup

Operating procedure

  1. If the project is linked with the configuration management system, get the edit permission for the file to be cleaned up.
  2. From the ribbon, click File> Information> Managing project files> File cleanup to open the File cleanup dialog.
  3. The project file and the divided model file are displayed. Check the target file and click the [OK] button.

attention

  • Warning messages No.1 and No.2 are not subject to cleanup. If you want to delete unnecessary data related to them, follow the corrective action for each.